Wearable electronic device with multiple detachable components

ABSTRACT

Disclosed herein is an electronic device with multiple independently functional components capable of sharing information through a connector channel that in one embodiment is worn on the body of the user with automatic attachment and detachment capability including via external communication or command.

This application is a continuation application of U.S. patentapplication Ser. No. 14/339,154, filed Jul. 23, 2014; which is acontinuation application of U.S. patent application Ser. No. 13/674,526,filed Nov. 12, 2012, now U.S. Pat. No. 8,805,441, issued on Aug. 12,2014; which is a continuation application of U.S. patent applicationSer. No. 12/163,878, filed Jun. 27, 2008, now U.S. Pat. No. 8,326,353,issued on Dec. 4, 2012; which application claims the benefit ofProvisional U.S. Patent Application No. 60/946,618, filed on Jun. 27,2007, and Provisional U.S. Patent Application No. 60/965,104, filed Aug.17, 2007, each of which is incorporated herein by reference in itsentirety.

FIELD OF THE INVENTION

At least one embodiment of the present invention pertains to mobileelectronic devices for communication, entertainment and/or organizationsuch as advanced mobile phones and other similar devices, and moreparticularly, to a mobile device with customizable functionality andform factor.

BACKGROUND

Consumer electronic devices such as mobile electronic devices haveundergone significant technological advances in recent years.Availability of advanced silicon technology, processing power, memoryand advanced input/output (I/O) and display systems as well as anincreasing level of communication bandwidth. including next generationwireless cellular as well as WiFi/WiMax wireless broadband technologies.enable the building of more-sophisticated devices.

Currently the majority of device innovations concentrate aroundincreasing the computing capability of wireless handsets. In some cases,wireless handsets of today are more powerful than supercomputers ofdecades ago. More memory, processing power and bandwidth are availabletoday, and the end consumer is able to generate and receive orders ofmagnitude more information compared to just a few short years ago.However, innovations in the areas of customization, organization andadvanced services remain behind the computational power increases. Infact, since the first major PDAs were introduced nearly 20 years ago,there has been little done to solve the organizational needs ofconsumers besides having access to an electronic version of a papercalendar. Despite the many available electric devices, the majority ofthe population is still relying on paper calendars due to their ease ofuse, reliability and lower cost and the few additional benefits offeredby their electronic counterparts.

The architecture of advanced mobile devices in the prior art is a highlyintegrated solution which does not allow for modularization anddetachability of components. The goal of most advanced mobile phonedesigns is to maximize the computing power of the device to support asmany features as possible and allow for future programmability andapplication development. This dictates a very high level of integration.At the core of this architecture is a high-powered integrated processorthat controls all processes within the mobile device. The integratedprocessor incorporates multiple micro-processing cores and digitalsignal processors enabling the device to run as a general purposemachine. The architecture generally utilizes a hybrid approach tocontrol the various components and programs running on the device.Overall it employs a PC-like environment with a general purposeoperating system (OS) which is capable of running any number of programswhich comply with its OS standards.

On the other hand, it needs to incorporate mechanisms for support ofreal time applications such as phones. Building a general-purpose engineto accommodate future programming and application capabilities as wellas making the device broadly applicable to a large number of usagescenarios by various device manufacturers inherently requires asignificant amount of overhead, significant wasted memory and computingresources, both passively as well as during runtime, to accommodatemostly unused features. It also significantly increases the effectivenumber of clock cycles per useful operation, the clock frequencyrequired to run the device in order to obtain a reasonable response timefor critical application steps, resulting in significant powerconsumption and cost.

To accommodate the general-purpose characteristic of the architecture, asignificant number of compromises are made, and as a result, theperformance of frequently used features can suffer due to interruptionsand accommodations made for such general-purpose items. In some cases,this has led to phones that take a long time to boot up, thusjeopardizing the main features of the device. In some cases, they drainthe device battery to an unacceptable level, disabling criticalfunctions such as emergency calling as well as increase the turn-on timeand device response time to a point of noticeable difference and delayin human interaction, especially upon starting up the device,eliminating the highly desired instant-on feature of the device.

FIG. 1 shows the block diagram of an example of the currentarchitecture. The integrated processor includes a number ofsub-processors, such as general purpose programmable computing cores anddigital signal processors, memory blocks, and drivers for a large numberof peripheral devices which may be attached to the device. Advancedmobile devices are designed to provide maximum integration and providemaximum programmability. The functionality needed by the majority ofmobile consumers, however, does not include an arbitrarily large numberof features and applications.

SUMMARY

One aspect of the technique introduced here is a mobile device thatincludes a core engine to control operation of the mobile device, and aplurality of modules coupled to the core engine, where each module isdedicated to perform a different one of a plurality of functionalityclasses of the mobile device, and each of the plurality of modulescontains its own processing element and memory. The mobile device hasuser-customizable functionality according to a user's needs and/ordesires. The mobile device may be in the form of a multi-function mobileelectronic system with distributed memory and processing elements. Suchsystem can include functionally distinct and independently operableintelligent sub-systems (e.g., modules) which together form amulti-functional mobile electronic system while sharing information withand/or through a master subsystem (e.g., a core engine). The sub-systemscan also share a data exchange block. The sub-systems can further sharetag information with and/or through the master subsystem. The system iseasily extendable to add additional functionality by adding additionalfunctionally distinct and independently operable sub-systems.

Another aspect of the technique introduced here is a mobile device witha user-customizable physical form factor. The mobile device may be inthe form of multi-function mobile electronic system with distributedmemory and processing elements, with the ability to attach and detachfrom the main system chassis (housing) at the manufacturing stage,assembly stage, post-packaging, or post-sale stage. The functionallydistinct and independently operable intelligent sub-systems togetherform a multi-functional mobile electronic system while sharing taginformation with and/or through the master subsystem via sharedconnectors, with applicable control signals to enable such sharing.

Another aspect of the technique introduced here is a mobile device withone or more detachable intelligent displays for communication to, and/oras access to, mobile device and/or other devices. Further, a mobiledevice can be shared through use of such intelligent detachabledisplays. Independently operational small module displays can becombined to form a large display for the mobile device. The mobiledevice may include, or have associated with it, a plurality ofindependently operable display devices, which are combinable to form asingle larger display device for the mobile device.

Another aspect of the technique introduced here is a time-basedinformation system (TIBIS) with event-based storage, access andretrieval functionality, which can be used in a mobile device such asdescribed above and/or other type of processing system. The TIBIS caninclude information storage and organization (i.e., a file system) thatis based on time instead of file locations in a directory. Further, itcan include temporary storage and organization of event, informationtags, or content in user-specified or machine-defined time intervals ina short-term memory (STM). It further can include long-term or permanentstorage and organization of events, information tags, or content inuser-specified or machine-defined time intervals in a long-term memory(LTM). Such long-term or permanent storage and organization of event,information tags, or content may be implemented with no ability torewrite the memory. The STM may be implemented as local non-volatilememory of the mobile device. The LTM may also be implemented asnon-volatile memory, which may be local memory of the mobile device,which may be removable, or it may be remote memory on a network.

The TIBIS can include a method for capture, storage and retrieval ofinformation in an information storage device such as a mobile electronicsystem based on a multi-category tagging mechanism covering temporal,geographical/location, context as well as user-defined concepts. Thiscan involve generation, storage, distribution of multi-modal tagging ofevents in an electronic apparatus such as a mobile information device.It can also include a method for fast hardware-based search andretrieval of information based on the multi-modal tag system. The TIBISprovides information archiving based on time-based organization withoutdisk fragmentation, the need for multiple backup, or the possibility oftampering with data.

BRIEF DESCRIPTION OF THE DRAWINGS

One or more embodiments of the present invention are illustrated by wayof example and not limitation in the figures of the accompanyingdrawings, in which like references indicate similar elements and inwhich:

FIG. 1 is a block diagram showing the architecture of a mobile device inthe prior art;

FIG. 2 is a block diagram showing an example of the architecture of amobile device in accordance with the techniques introduced here;

FIG. 3 illustrates an example of the operation of the giant statemachine (GSM);

FIG. 4 illustrates the data flow between various functional modules andthe communication/entertainment/organization (CEO) engine in a mobiledevice;

FIG. 5A shows a functional module in a micro-BGA package, such as may beassociated with one embodiment;

FIG. 5B shows an example of the display of a mobile device such as maybe used in conjunction with the functional module in FIG. 5A;

FIG. 5C shows an example of a circuit board on which are mounted variousfunctional modules and a CEO engine;

FIG. 5D shows an example of an external view of the assembled mobiledevice, according to the embodiment of FIGS. 5A through 5C;

FIGS. 6A and 6B show embodiments of functional modules connecting to acircuit board at the factory;

FIG. 7A shows a functional module in detachable form, such as may beassociated with another embodiment;

FIG. 7B shows a display device that may be used in conjunction with thefunctional modules in FIG. 7A;

FIG. 7C shows multiple detachable functional modules connected to aconnector channel;

FIG. 7D shows a CEO engine and other components of the mobile deviceconnected to a circuit board;

FIG. 7E shows the functional modules and connector channel of FIG. 7Cmounted within a device housing;

FIG. 7F shows an example of an external view of the assembled mobiledevice, according to the embodiment of FIGS. 7A through 7E;

FIG. 8A shows an independently operable functional module with its owndisplay, in detachable form;

FIG. 8B shows multiple functional modules such as shown in FIG. 8A,connected to a connector channel;

FIG. 8C shows an example of an exterior view of a mobile device whichhas multiple functional modules such as shown in FIG. 8A, each with itsown display, which collectively can be operated as a single largerdisplay;

FIG. 9 shows a cylindrical mobile device with additional modules asstackable disks;

FIG. 10 shows a radial module configuration device with a central coreand housing for additional modules around the core;

FIG. 11A shows a wrist-top mobile device with an additional detacheddisplay unit; FIG. 11B shows a wrist-top mobile display with anadditional detached display unit; FIG. 11C shows a mobile device, awrist-top device, an ent/info/connectivity device with additionaldetached displays of different display features with wirelessconnectivity; FIG. 11D shows a mobile device with multiple detacheddisplay units for multiple users;

FIG. 12 is block diagram illustrating the Horizontal RepositoryArchitecture;

FIG. 13 shows an example of the generation and processing of tags in thetime-based memory organization;

FIG. 14 shows the data flow of the modularized mobile architecture witha time based information system (TIBIS™);

FIG. 15 shows the TIBIS operations facilitated by the CEO engine;

FIG. 16 illustrates an example of an algorithm for tag and contentsearches; and

FIG. 17 shows a system level-view of hardware and software elements in amobile device in accordance with the techniques introduced here.

DETAILED DESCRIPTION

References in this specification to “an embodiment”, “one embodiment”,or the like, mean that the particular feature, structure orcharacteristic being described is included in at least one embodiment ofthe present invention. Occurrences of such phrases in this specificationdo not necessarily all refer to the same embodiment.

A “mobile device”, as the term is used herein, means any device that isdesigned to be worn by a person, carried in an article of clothing orpersonal accessory (e.g., a purse), or easily carried in one hand by aperson. As noted above, the functionality needed by the majority ofusers of mobile devices does not include an arbitrarily large number offeatures and applications. Having the technology for massive computationassembled at many places, it is desirable to alleviate the mobile devicefrom area- and power-consuming functionality that is available almosteverywhere. In its place, it is desirable to make the mobile deviceperform the functions that are essential for mobility (e.g. voice, text,video capture, storage and display, etc.) in the most robust fashion.

The present invention provides a robust solution for addressing theorganizational needs of mobile consumers by providing, among otherthings, a new customizable mobile device, optimized for mobile usage,which provides customizability, lower cost, lower power, and betterpedormance. A time-based intelligence system (TIBIS™) is alsointroduced, which allows for robust storage, access, and processing ofinformation on the mobile device.

(1) Customizable Mobile Device (C.E.O.™)

(1A) Mobile Device with User-Customizable Functionality

The present invention offers consumers the ability to choose thefunctionality and form factor they desire in a mobile device. Each ofthese modules may be dedicated to perform a specific type of user-levelfunctionality, such as voice communication, text, video capture,storage, display, location determination, games, etc. “User-level”functionality means functionality that is directly perceivable by ahuman user of the device.

The approach introduced here allows users the flexibility of using thecomponents that they need and none of the ones that they do not need,allowing for customizability and reduction in cost and powerdissipation.

Communicate/Entertain/Organize (C.E.O™) is a mobile platform introducedhere that allows people to communicate, entertain, and organize theirmobile life. The mobile device uses “ultra thin client” architecturewith custom-designed dedicated hardware for functions that need to beperformed on the handset. The design removes the need for a multitude ofprogrammable multi-function cores. This architecture results in highperformance, fast response time, and very low-power consumption. Inaddition, this architecture allows users access to a rich set ofcustomized applications based on their needs from the network, ifneeded.

One aspect of CEO is a modularized architecture for a mobile device(“Modularized Mobile Architecture”). The modularized nature of thisarchitecture allows for the ability to choose the functional modulesthat are combined to make a mobile device. This gives the ability toexchange and upgrade the functional modules over time. For thisfunctionality, customization and flexibility, a level of service isestablished with the customer (user) making the device of their choiceand giving the customer the ability to upgrade easily over time. Forexample, one functional module may be a communication module, which canbe upgraded if a faster communications technology becomes available tothe user, without the need to discard the entire mobile device.

FIG. 2 shows a block diagram of the Modularized Mobile Architectureaccording to one embodiment. The architecture separates out thefunctional blocks for each major device function and removes large,power consuming general purpose processors as well as the accompanyingshared memory hierarchy. Each functional module has its own dedicatedprocessing element (PE) and memory element (ME). The PE in eachfunctional module can be, for example, a programmable microcontroller,application-specific integrated circuit (ASIC), programmable logicdevice (PLD), or other similar device or a combination of such devices.The ME in each functional module can be, for example, random accessmemory (RAM), read-only memory (ROM), flash memory, or other type ofmemory, or a combination of such types of memory.

The functional modules can include, for example, any one or more of: acommunication module (e.g. 3G), audio module, video module, GPS moduleand game module. By optimizing the PE to the specific functions beingperformed by its functional module, it is possible to reduce theunderlying area and power consumption of each functional module.Performance of each PE is better than the unified processing case withan integrated processor due to function specialization as well as thereduction in area, which facilitates timing requirements, placement andreliability of the PEs within each module. In some cases the performanceand area savings are such that they allow for choosing an oldergeneration process technology while still maintaining the performancerequirements, which results in reduced manufacturing costs and overallcomponent cost of the device.

By providing separate memory for each functional unit, the majority ofissues with memory bottleneck are eliminated. Each functional module hasits own dedicated memory and MEs are not shared resources, as is thecase in traditional architectures. In other words, instead of separatememories for instruction and Data for the whole system, thisarchitecture allows for separate memory for each application-specificarea for the mobile space.

This approach has many advantages over traditional architectures. Itallows for robust information sharing mechanism among functionalmodules. In addition, it is possible to make significant improvements tothe choice of technology used for the memory blocks to properly optimizefor the type of data being stored in that specific memory element.Depending on the type of stored data and usage patterns, it is possibleto vary the block size and read and write specifications of each memoryelement. The architecture preserves and enhances the functionality ofeach individual functional unit while allowing these units tocommunicate with extremely low overhead.

The CEO engine is a very efficient hardware-optimized engine thatfacilitates the communication between the modules and provides thecentral functionality of the mobile device. The mobile device isdesigned to accommodate specific functionalities for the mobileenvironment rather than provide unlimited programmability. Thesignificant manipulations of data that occur in the mobile device are aset of operations designed for the functionality of the device, such asthe following:

CAPTURE

STORAGE

RETRIEVAL

SEARCH

DISPLAY

TRANSMIT

Making these operations extremely efficient and not allocating resourcesfor unused functionality greatly reduces cost, increases performancesignificantly and reduces power utilization. In a simplified manner, theCEO engine implements a Giant State Machine (GSM) which is designed tocontrol the device functionality in very high speed in pure hardware(i.e., without the use of software). An example of such an operation iscapturing an image from the camera module and sending the image out tothe wireless communication module, which involves Capture, Compress,Store and Transmit operations. The GSM orchestrates these operations bygenerating the appropriate control signals. FIG. 3 shows the GSMoperation for this example.

The Modularized Mobile Architecture allows for robust and intelligentsharing of information among functional modules instead of sharingresources, and it resolves one of the major overheads associated withmanagement of shared resource. A major part of the tasks performed by atraditional operating system (OS) is resource management and interruptcontrol. This allows the system to manage access to shared resourcessuch as memory. In the Modularized Mobile Architecture introduced here,the significant computational overhead associated with a traditional OSas well as the memory requirements to store active as well as passivecomponents of such OS is eliminated.

The memory architecture is designed so that a small portion of thememory contents in each functional module, namely a set of extracted andstored “tags”, are communicated to the CEO engine and to otherfunctional modules as needed (the memory architecture is described belowin relation to TIBIS). As a result, a very robust interface is developedbetween the CEO Engine and each functional module. This architectureallows for robust and intelligent sharing of information instead ofsharing resources.

FIG. 4 illustrates the data flow between various functional modules andthe CEO engine in a mobile device, according to one embodiment. The MEin each functional module is divided between working memory (WM) andHorizontal Repository Memory (HM). WM is preferably a form of RAM, whileHM is preferably a form of nonvolatile memory, such as flash memory.Each functional module communicates directly with the CEO engine, andthe CEO engine orchestrates any required interaction between functionalmodules. The CEO engine also generates the required permissions formodule designation for transmit and receive on the data exchange block.The data exchange block is a bus designed for fast, efficient transferof data among modules as necessary. An exchange interface unit isincluded in each functional module to allow for this communication. Thebit width, impedance, signal integrity and data transfer rates areoptimized for a given cost model, performance requirement, and availableconnector technology.

In one embodiment, programmable elements are included in the exchangeinterface unit in each module to allow for flexibility in the design.This programmability allows the signaling parameters to be adjusteddepending on the requirements for the best available technology. Forexample, it allows for sufficient buffering of data for proper assemblyand disassembly and timing of data to match the best available signalingfor the data exchange block.

While the individual memory blocks shown in FIG. 4 can be physicallyseparate memory devices, this is not a requirement, and the memory unitscan all or partly reside on the same physical memory device; however,each memory block is distinctly assigned to a functional module, hence,there is no sharing of the same block of memory. Initially the memoryunits are assigned to various functional modules based on theapplication as well as user requirements. The memory allocation can bedynamically re-allocated based on need. For example, when a functionalmodule is not being used, the associated memory can be allocated toother modules, or if a functional module has a need for expanded memoryusage and there is unused memory assigned to other functional modules,it can be re-allocated. In addition, the modular architecture allows forthe ability to upgrade the memory for each functional module as needed.

(1B) Mobile Device with User Customizable Physical Form Factor

The mobile device architecture introduced above can integrate variouselectronic modules into a single customized device. The ModularizedMobile Architecture allows for customization of device functionalitybased on user preferences. This customization can occur at any ofseveral levels:

-   -   1. The modularized architecture can be applied to the design of        the mobile device at the chip level. Each functional block is        optimized and the chosen modules are all implemented on one        chip. This allows for customization at the chip level and        results in highest performance but least flexibility.    -   2. The choice of modules can be made at the package level, where        selected functional modules fabricated on small micro-boards are        assembled to produce the device. Alternatively, advanced        packaging techniques are used to integrate each functional        module on a single package (e.g. multi-chip-module,        ball-grid-array (BGA) package, etc.). Selected functional        modules are assembled to build the customized mobile device.        This level of customization is done at the factory and offers        customization to the user without significantly altering the        manufacturing process. In this implementation, the device is        customizable by the user at purchase order time and the        modularity of the design is exploited at the factory to provide        the user the customized solution desired; however, the device is        not physically detachable by the user, so its flexibility is        limited since the user can not reconfigure the device after        delivery.    -   3. The third method of delivering customization is the most        flexible. In this approach, the functional modules and the        mobile device core housing are delivered to the user and the        user can attach or detach some of the modules at the point of        use. This allows for the customization to occur both at the        functional level as well as the physical level and offers the        most flexible option.

The customized mobile device allows users the flexibility of using thecomponents that they need and none of the ones that they do not need, byallowing for the integration of a variety of modules that performcommunication, computing, and a variety of input and output functions.It results in lower cost and power dissipation. It can provide freedomfrom the choice of service provider by allowing the user to keep desiredelectronic components as well as stored information while having thefreedom to change service provider (i.e., to change the communicationmodule). It also removes the requirement of building multiple standardradio devices on the same mobile device (e.g. cellular, WiFi,Bluetooth); only radios that the user plans to use are added. It alsoprovides an easy upgrade path for the components that the user desireswith new nodes of technology without the need to replace the entiredevice.

Each module can be a functional module that is operable only within amobile device, or it can be an independently (individually) operablecomponent. Independently operable components have some level of userinterface as needed by that module and can be used on their own. When amodule is inserted into the mobile device, it has access to an expandedset of functionality for storage, display, I/O and communicationfacilities. While some modules can connect together directly (e.g., theaudio module can be directly connected to the communication module), themodules are typically connected to the CEO engine on the mobile device.

FIGS. 5A through 5D show an embodiment of a mobile device which hasfunctional modules integrated at packaging level. Each functional moduleis integrated in a micro-ball grid array (BGA) package. FIG. 5A shows afunctional module in a micro-BGA package. The functional modules and theCEO engine are integrated on a printed circuit board (PCB). FIG. 5Cshows an example of a PCB on which are mounted various functionalmodules and the CEO engine. The interconnections are made through therouting channels on the PCB. The PCB is then encased inside the mobiledevice housing. The display is placed on top surface of the device andattached to the PCB through the display connector. FIG. 5B shows anexample of the display of the mobile device such as may be used inconjunction with the functional module in FIG. 5A. FIG. 5D shows anexample of an external view of the assembled mobile device. FIGS. 6A and6B show embodiments of functional modules connecting to a PCB at thefactory.

FIG. 7 shows another embodiment of a customized mobile device, which hasdetachable functional modules. FIG. 7A shows a detachable functionalmodule. In this embodiment, the functional modules do not haveindividual displays. Four modules are connected to the device throughthe connector channel placed at the center of the device. FIG. 7C showsmultiple detachable functional modules connected to a connector channel.The CEO engine is placed on a PCB at the bottom of the device and isconnected to the modules through the connector at the bottom of theconnection channel. FIG. 7D shows a CEO engine and other components ofthe mobile device connected to a circuit board. The modules, connectorchannel, and PCB are housed inside the mobile device housing. An LCDdisplay is placed on top of the device. FIG. 7B shows a display devicethat may be used in conjunction with the functional modules in FIG. 7A.FIG. 7E shows the functional modules and connector channel of FIG. 7Cmounted within the device housing. FIG. 7F shows an example of anexternal view of the assembled mobile device.

FIG. 8 shows another embodiment of the customized mobile device withdetachable components. In this embodiment, each of the functionalmodules has its own individual display device. The modules are slippedinto the mobile device housing and connect to the connection channel asdescribed above. On top of the mobile device, there is an opening in thetop surface of the housing for the display units. These modules areindependently operable and each module uses its own small display in thestand-alone mode of operation. The CEO engine keeps track of the modulesthat are connected and sends the appropriate control signals to thecircuitry for resizing the image appropriately. Once the modules areconnected to the mobile device, the CEO engine recognizes the individualdisplay units that are connected to the device and resizes the screen sothe mobile device has a single large display.

FIG. 8A shows a detachable, independently-operable functional modulewith its own display. FIG. 8B shows multiple functional modules such asshown in FIG. 8A, connected to a connector channel. FIG. 8C shows anexample of an exterior view of the mobile device which has multiplefunctional modules such as shown in Figure BA, where the individualdisplay devices of the functional modules collectively can be operatedas a single larger display.

All of the functional modules can be powered from the power supply ofthe mobile device. An independently operable module also has its ownon-board battery which is recharged when the module is connected to themain unit.

The module connectors are designed to facilitate the connection betweenthe functional modules and the CEO engine through the data exchangeblock. In the modularized architecture of the design, the data isexchanged between modules under the control of the CEO engine. The sizeand characteristics of the data buses from different modules may bedifferent. Instead of designing a custom connector for each module, aunified connector is designed to support all available modules in aparticular configuration. The choice of connector depends on the formfactor and bus speed. One option is a high-speed serial bus with a smallfootprint. Another option is a parallel bus for ease of signal routing.In one embodiment, a custom low-profile, parallel edge connector isused. This gives the flexibility of supporting a large number of moduleswith varying bus sizes and facilitates interconnection between themodules and the main core. Data at the I/O interface of each module isassembled or disassembled to match the connector's data bit width andtiming. The CEO engine facilitates the data exchange between the modulesthrough appropriate control signals.

In addition to module choice, the user has the choice of device shape,size, and configuration. The device can have any of a variety of shapes,such as square or rectangular, round, or cylindrical. Modules can beassembled in any of a variety of ways, such as connecting sideways toanother module or vertically as stackable disks.

FIG. 9 shows an embodiment of a cylindrical mobile device withfunctional modules connected in a stackable configuration. In thestackable configuration, modules connect on the side to each otherthrough the connection channel in the device housing. In anotherembodiment, the connections between the stackable modules can be on topand bottom of modules. The connectors are retracted mechanically beforea module is connected or disconnected from the device. Modules canconnect together directly as well as modules dropping into a devicehousing/carrier/chassis.

Other arrangements of modules are dictated by the desired industrialdesign of the mobile device. FIG. 10 shows a round device with a centralcore and housing for additional modules around the core. In this case,the modules are inserted inside the device housing and any unused moduleis left with an empty housing to preserve the overall look of thedevice.

The user also has the additional choice of having the assembled mobiledevice in a wrist-top configuration (worn as a watch), a clip-onconfiguration where it is worn on a belt or armband, a pendantconfiguration, as an ear-top device or a handheld device.

In one wrist-top configuration, such as shown in FIG. 11, when a phonecall is initiated or received, the unit slides out of the wristband 111and the user holds the device to the ear. Alternatively, the unitincludes an optional small pull-out microphone/speaker unit that is usedduring calls to keep the incoming phone calls private. FIG. 11 shows awrist-top mobile device, with an example of different types ofinformation/functions shown on the display 112 (e.g., “STATS”, “CALLS”,“EMAILS”, “AUDIOS”, “STILLS”, “VIDEOS”, “PROCESS TRACKING”, “PLANS”,etc.).

Other detachable modules include audio and video recording and playbackmodules, GPS tracking and location broadcast module, game module, etc.The platform is also designed for other consumer electronics devicefunctionalities that can be added over time such as bio sensors, healthmonitoring devices, environmental sensors, etc.

In addition to modules that support common mobile functionality such asaudio/video modules, GPS and games, the platform introduced here alsosupports other consumer electronics device functionalities that can beadded over time, such as biosensors, health monitoring devices,environmental sensors, etc. The Modularized Mobile Architecture allowsfor the functionality of the modules to be developed and optimizedindependently and can easily integrate essentially any module bymodifying the interface to fit the mobile device interface.

Connection made through abutment/overlay/slide through. Modules canconnect together directly as well as modules dropping into a devicehousing/carrier.

The detachability of components occurs at the device level, board-level,and package-level. At the device level, a module is detached by the userdepending on the mode of operation. At the board/package level, asection of the board is detached (candy-bar format) as well as employingadvanced packaging techniques (including multi-chip module, multi-chippackaging.) These are employed to achieve the highest cost and powerefficiency for the end customer based on their final deviceconfiguration at the BTO (built-to-order) level without significantlyaltering the manufacturing process.

While many detachable modules can be independently operable, that is nota requirement. For example, a single memory or display module may not beoperable on its own, and there are modules that are supporting accessoryhardware for another module. A “super module” can incorporate a numberof module functions that are commonly used together.

In one embodiment, the MEs of each individual functional unit areremovable and swappable. This allows for quick and fast transfer andsharing of data among devices, as well as quick personal security andbackup feature.

Modules in detached mode which are connected to a communications modulecan be reconfigured over-the-air to support an array of functions in thestand-alone mode. This can be achieved through the use of fieldprogrammable logic as well as registers which can be updated remotely toallow for modified mode of operation of the module in a power efficientmanner.

Location Tags on Items Activated and Tracked through Cellular PhoneNetworks

Similar to RFID tags attached to items so their location can beidentified, except the tag is equipped with a stripped down version of acell phone. It can be activated through the cell network and it willsend back a signal identifying the location. The location ID can be fromcellular tower information or a GPS receiver can also be integrated onthe device. In one embodiment, the device is generally off but whentracking is needed, the user turns on the device. In another embodiment,the device is activated continuously and can be tracked if lost or thereis a need to locate the device. In another embodiment, the device turnson at a predetermined time interval and looks for a useable wirelessnetwork to send its location info. If one is not found, it will try at alater time interval. This is a low-power device but to power the device,a regular battery can be used. If it is attached to an electronic mobiledevice, it can be powered up by the battery of the device. A solarbattery can also be used to power the device and continuously rechargethe device. In another embodiment, the device is turned on remotely ondemand. Other wide-area communication technologies such as WiMax can beused as the tracking network once they become widely adopted. In oneembodiment, the tag device can attach to a special insert so the tag canbe used as a small cell phone for voice or text communication if needed.In case of an electronic device that is stolen, the tag can beprogrammed to disable the device.

Wristband Mobile Device, Cellular Phone Headset and Wrist Combination

One of the form factors that the user can select is a mobile device thatis worn on the wrist just like a wrist-band watch is. The watch isuniversally used as a time keeping device. Most people carry it withthem all the time. This invention is a mobile device that contains acell phone as well as other electronic components of choice such as acamera and is integrated into the form of a wrist-band device that theuser can put on in the morning and carry with them through the day. Thedevice can include a microphone and speaker or a headset. For additionalprivacy, the device could also pick up voice wirelessly through sensorsaround the face/neck to pick up voice/muscle movements. The keypad canbe on the device (touch pad, pull-out/clip-on keypad, rolled-up keypad)or projected from the device onto an external surface or a roll-upscreen.

Wireless Communication Device in Earphone

Another embodiment is a mobile communication device that fits in, on, oraround the ear. It includes the communication device (e.g. cell phone)as well as the speaker and microphone. It can include avoice-recognition system so phone numbers and other information can bespoken without the need for a keypad. Although the invention does notpreclude a more conventional unit with a keypad that after dialing canbe put around the ear, removing the need for separate headphones or theuse of small keypads with wireless connectivity with the phone.

Privacy Microphone for Mobile Devices

Another embodiment is a microphone for any voice-driven device such asmobile phones where the voice is picked up by sensors placed on theface/neck. In one implementation, the sensors pick up voice in very lowvolume, in another implementation, the sensors pick up voice throughmuscle movements. This invention provides for private conversationswithout the need for using alternative input sources such as text.

Mobile Device w/Battery Recharged (Continuously) with Human Motion

Another embodiment is a mobile device whose battery is recharged bymotion. In one implementation, the mobile device is worn by the user(e.g. on the wrist) and the battery is continuously recharged throughthe motion of the human body. In an alternative implementation, thedevice is moved around for a period of time to recharge. In anotherimplementation, the device includes an integrated/detachablemicro-mechanical crank that is cranked for a period of time to rechargethe battery. Depending on the power requirements of the mobile device,the mechanical recharging of the battery could be a supplement to astandard battery used in the device.

(1C) Detachable Intelligent Display

Mobile devices are faced with a continuous need for larger display sizesfor certain applications, such as viewing of photos, videos, surfing theweb, etc. The large size of the display adds significantly to the size,power dissipation and cost of the mobile device. However, in mostapplications there s not a continuous need for a large display, suchthat the associated additional weight, size, and power dissipation areunnecessary. The technique introduced here overcomes this barrier byseparating the requirements of the device from those of the displayunit.

In this technique, the mobile device has a very small display or nodisplay at all. This is the normal mode of operation, generally themobile mode of operation. As a result, the mobile device is small andhas low power dissipation. A group of larger displays are designed andmade available to the user upon request. These displays vary in featuressuch as size and display resolution. The initial display design can bethe size of a business card to be carried in a wallet and used in asimilar manner. This display size is adequate for a large number ofusers in a mobile environment. This detached display can be attachableto the mobile device via direct wire connection or via wireless link.FIGS. 11A, 11B, 11C, and 11D show a wrist-top mobile device with anadditional detached wallet-sized display unit 113. The CEO engine plusenvironmental sensors and/or biosensors are located on the bottom of themobile device.

Another size display is a letter size display, which can be carried inthe user's briefcase among other paperwork and file folders. When a needfor such a display arises, such as for editing, viewing documents,photos or videos or presenting such material to a larger group, theletter size is the more appropriate usage model. As in the case of thewallet size display, the connection mechanism is established either viawires or wirelessly depending on the customer's selection at the time ofordering.

In the wireless mode, the display is turned on and is held by the userfor viewing, totally detached from the unit. The mobile unit staysnearby, for example in a pocket, purse, or worn on the wrist. The useronly holds up the display, which is smaller and less bulky, while havingaccess to all the functionality of the mobile device.

The display is powered by its own rechargeable battery which isrecharged with the mobile unit. The display is able to draw power fromthe handheld device through a wired connection. This is also the mode ofoperation if the display does not have its own battery (e.g.,ultra-light model). In cases where the display unit has a charged upbattery but the mobile device is low on battery charge, the mobiledevice can draw power from the display unit.

Since the display unit is totally separate from the mobile device, withappropriate security measures the user has the possibility to use anyappropriate display units other than his own. This means that if for anyreason the user does not have access to his display unit, the user canborrow, purchase or rent another display unit.

Text entry on the mobile device can be accomplished through any ofseveral methods, such as through a software keyboard on a touch-screendisplay, or a small physical keyboard that is stored in the wallet, etc.which can also be attached to the display.

In addition to mobile devices, the display can potentially be used withany other electronic equipment, such as a DVD player which is equippedwith the proper communication technology. In this scenario, the user canconnect to any information/entertainment device such as a PC, a DVDplayer, etc., and with proper authorization, can view theinformation/content on the display.

In one embodiment, several small display units stack up or fold and whenneeded, they can be opened up where the small displays connect togetherto form a larger display. Alternatively, additional small displays canbe attached to an existing smaller display to form a single largerdisplay.

The detached display allows for a new usage model for sharing ofinformation/shared viewing of content. Multiple display units can beprovided to users so they can access the information/content on a singledevice. Security measures can allow for authentication of the displayunits which can connect to the device. In addition to point-to-pointconnectivity, multi-cast connectivity can allow users to access theinformation on the device. The system allows for the individual displayunits to act as separate application windows on the mobile device (withproper security features which control guest access). As a result, eachdisplay unit can allow the user to independently access authorizedservices, such as web access, etc. This allows multiple usersconnectivity and content access without the need for individual devices.This technology provides a robust solution to applications such asmultiplayer gaming, presentations, classroom/conference settings/on-thespot access to mobile services, etc.

(2) Time-Based Information System (TIBIS)

(2A) Event-Based Storage, Access & Retrieval

The techniques introduced here include TIBIS, a time-based informationsystem of data organization. TIBIS is particularly suited toimplementation in a mobile device such as described above, although itis not limited to a mobile environment. The current PC model ofentering, saving and organizing files grew out of the transition fromtypewriters/word processors/calculators. Although the sophistication offile systems and their many different formats have continued to grow,the fundamental design element for these systems remain packing the mostamount of information in the least amount of space and facilitate accessto the information while providing data integrity based on theunderlying memory hierarchy of the system. Available storage systemslack a higher level of awareness and intelligence, which is particularlyevident in mobile device usage scenarios.

While “content” and general-purpose programming/flexibility forapplications remains of primary concern in a PC environment, in a mobileenvironment the primary factor is time. People typically use mobiledevices to have access to information on-the-go and to save time.Features of TiBIS allow a hardware and software environment to providerobust storage, integration, recognition, recall and display oftime-based activities and events in a user-customizable format.

Currently, most data is stored in electronic form in files. These filesare organized in various directories or folders based on the type offile or the relationship of the content of files. The files have a timestamp associated with them. Other than looking up the time stamp whenone looks at a file, the only other thing one can do with the time stampis to sort the files based on time in a given folder or directory.

In addition, files are randomly written in different areas of memory.When a file is deleted, an area in memory becomes available where thefile was written before. As more and more files are deleted, more areaopens up in memory, but the open (free) areas are not contiguous. Thisresults in fragmentation of data in memory, which results in a slow downof data access.

With TIBIS, all files are organized based on time, with the granularityof time determined by the user. The user can have control over periodicstoring of specific information, store information through a direct usercommand, or any other user-defined mechanism. Activities, multimediafiles, etc. are organized in a time snap-shot. As new pieces ofinformation are received or generated, they are written sequentially inmemory. Since data that is recorded (“the past”) cannot be modified bythe user, the stored data is permanently stored in memory. This requiresa large amount of memory over time. TIBIS provides a way to ease therequirements on the size of memory and store only information that theuser will need in the long-term, while allowing the user to continue tohave a snap-shot of all relevant information.

The TIBIS system is organized around two types of memory. One is calledthe Short-Term Memory (STM) and the other Long-Term Memory (LTM).Initially, information is recorded sequentially in STM. The size of STMis determined by the user and can be very short or very long, dependingon the application and user preference (e.g. hours, days, weeks, etc.).During a predetermined amount of “inspection” period, the user has theoption of erasing from STM any information deemed unimportant (e.g. anincoming junk email, erroneous file, etc.). In one implementation, theinspection period is chosen to be the amount of time it takes for theSTM memory to be filled. At the conclusion of the inspection period, anyremaining data is sequentially written to LTM. Any data that is erasedfrom STM memory is not written in LTM. Once data is written in LTM, itcan no longer be changed. The option to give the user the ability toerase LTM can be provided by an administrator of the system. If the userexercises the option to erase any part of the time snap-shot in LTM, thememory for that part can not be re-used by other data.

In one implementation, the data in STM can be shifted up through memoryas new data is brought in or data can be shifted up once a section ofmemory is cleared and becomes available. In this way, data always getsstored in contiguous memory locations sequentially according to the timethe data is stored, and data-hold time calculations are simplified.

In addition, this memory architecture is designed to allow for userprogrammability of memory configuration, hybrid time-sector tagging ofmemory, dynamically varying the time granularity, and finer resolutiontime snap-shots inside another snap-shot.

In this system, problems with memory fragmentation are thereforeresolved, since no rewriting is done in previous segments of memory anddata is always written in contiguous sections of memory. In addition,since the memory is written sequentially based on time, one needs tobackup any part of memory only once, since contents of past memorycannot be modified (except where the user is given the option ofdeletion). Therefore, periodic backups of data or changes to the dataare not needed.

One way to deal with files that are modified over time is to keepmultiple copies of files at each instance where a new version is saved.To reduce memory space, an alternative method can be used where thefirst instance of the file is saved, and each time the file is modified,a modification list from the previous version is saved. To improveaccess time, the system can keep a copy of the last modified version infull so no reconstructing is necessary when data is retrieved frommemory for editing. This intermediate version is then deleted. Data canalso be referenced backward with changes from the latest versions.

TIBIS also provides benefits for data security and information audit.Since the system stores time snap-shots, it is straightforward to reviewpast activities and information. The system also makes it easy to auditpast information and activities such as financial transactions, etc.

TIBIS also makes it possible to view a snap-shot of user's life, basedon what information the user has chosen to include. This then becomespart of a digital journal of the user's life.

TIBIS removes static applications and content from being the centralfactor in device architecture. Instead the primary design element of thesystem is capturing and providing “relevant”, “useful” and “timely”event information to the user. Each time snap-shot contains a record ofall activities the user chooses to record, store, and/or track for theselected time granularity (e.g., daily, hourly, weekly). A timesnap-shot records all relevant information, such as physical locationcoordinates of the mobile device (or other type device that isimplementing TIBIS), any information received, transmitted, captured,created or opened by the device, conversations of the user, etc. Theinformation can include any type of multi-media data such as audio,video, email, text, etc. The system has provisions for a set ofinformation repositories that include all files of the appropriate type(e.g., an audio repository includes all audio files generated, receivedor stored by the user).

FIG. 12 shows an embodiment of the Horizontal Repository Architecture(HM™) of TIBIS. Each functional module (e.g., audio, video, e-mail,etc.) of the mobile device (or other type of processing systemimplementing TIBIS) has its own separate memory. Each stored contentitem also has a tag which lists all the relevant information (metadata)for that item, which is stored along with the item in a repository. Allof the tags from each function's memory are collected for the selectedtime period (e.g., daily) and stored together as a super-block, or “timesnap-shot”, in STM. At the appropriate time (e.g., when STM is reaches apre-defined time limit), in one embodiment the user is prompted toexamine the tags and determine which contents and tags they wish topreserve. In the absence of additional user input, the mobile devicemakes the decision based on an initial programming default. In theaforementioned embodiments, the chosen contents of STM along with theaccompanying data as chosen by the user are written to LTM, and STM iscleared or overwritten. In another embodiment, the data moves through awindow of a given STM cycle, e.g. 30-days, while at the same time eachtime snapshot (e.g. daily) is transferred to LTM in a first-in first-out(FIFO) output manner. The time snap-shot has links to any blocks of datain the relevant repository that is accessed in the given time period.When data is moved to LTM, all content is saved in the LTM entry or theuser can choose to keep only the pointer to the content in therepository.

(2B) Memory Hierarchy & Time Based Architecture:

In implementing this unique storage and retrieval technology, HM unitsfor each device are provided to match the device's storage and accessrequirements. This means that individual functions' memory storage canbe changed over time, and different or same memory technologies may beused for different types of data storage and access requirements.

In addition to providing distinct and in some cases detachable,removable, expandable HM memory units, each stored item such as data,music, still photo or video is stored with a particular tag structure.FIG. 13 shows the generation and processing of tags in the time-basedmemory organization. Each tag is appended to the actual stored elementin a predetermined set of extended locations. A tag typically includesmetadata that answers one or more of the five questions: “what” (can beuser-defined), “when” (e.g., time/day/date), “where” (location of thedevice), “who” (e.g., sender and/or recipient of a message) and “which”(e.g., source). Each function of the device (e.g., audio, video, etc.)generates its own type of tag. For a given time period (e.g., one day),the various tags are collected into a single tag block, which is savedin STM. Note that there can be more tag categories than the abovesuggested five for certain applications.

The contents of STM can therefore be used to provide a complete “dayview” to the user for multiple days, or similar view for any otherselected time period. Upon a request for retrieval of data, a fastsearch mechanism is then able to retrieve the data element by hardware,and in some cases software, by comparing only the tags of data elements.In case a tag comparison results in multiple hits, the reduced set ofdata elements (tag hits) is then subjected to a further search in a muchreduced complexity and time.

An example of a simplified tag generation scheme is as follows: Upontaking a photograph with the still camera module, the locationcoordinates are retrieved automatically via the on-board GPS locationmodule. This information is then cross-referenced against the personaladdress space of the user as well as the calendar information todetermine the exact location where the user is likely to be. This can befurther clarified by posing a question to the user for a finalclarification. The “actual” verified location is then part of the tagassociated with the photograph. Further, the time and date is known,which is cross-referenced against the user's calendar and “dates ofimportance” file in the user preferences directory. This clarifies theexact occasion and can be even further clarified by posing a question tothe user. This information also becomes part of the tag. In trying toretrieve or recall the photo, the user only needs to remember a part ofthe tag to be able to access the desired photo or information ingeneral.

Further features of the tag can include character recognition as well aspattern and voice recognition. Upon storage, a sample of all suchavailable modalities of the file becomes part of the tag. In recallingthis information or in trying to organize and archive, over time userpreferences can be allowed to change to include something such aspresence of a certain person in the photo, rather than using the moresimplified versions of the tag.

If a typical storage element (type of file element) for a module is, forexample, 256 bits and a memory word is 16 bits, then it takes 16 rows ofdata to store this element. If the design parameters allow up to 20 bitsfor the data and tag space, then up to 64 bits can be used for a tag (4bits*16 words). If the storage element is 1 Kb for the same overall bitwidth of 16+4, then one needs 64 words to store that element. In thiscase one can have up to 256 bits for a tag.

In general, the tags are uniformly designed so that for most data typesand functional modules, one can go up to a certain maximum size tag. Forexample, if all one needed is 64 bits, then for the rest of the words,the tag can be either repeated or driven to an agreed upon level. Theimplementation is design dependent.

In certain embodiments, a tag is proportionally as wide as the ratio ofits functional module's typical data element size to the maximumrequired tag size. In this case the tag and data are proportionallyassembled and disassembled. In other embodiments, the tag may getappended to the first or last data word and recognized with anend-of-element flag. In yet another embodiment, the tag always getsstored in its entirety and then the data element begins.

In certain embodiments, the tags are fixed in size and the memory wordsize and depth is a design element based on each module's typicalelement size and timing requirements for the control signals. In somecases, the row of data to tag ratio is determined specifically for eachfunctional module and data type. Hence, customization happens at themodule level even for memory.

FIG. 14 shows the data flow of the Modularized Mobile Architecture withTIBIS, according to one embodiment. FIG. 14 is essentially identical toFIG. 4, except that it further shows the LTM in relation to the CEOengine and the functional modules. In at least some embodiments, the STMis implemented as memory that resides within the CEO engine. Further, inthe illustrated embodiment the LTM is separate from the CEO engine andis coupled to the data exchange block through separate control and datalines and to the CEO engine through separate control and tag lines. Inother embodiments, the LTM is implemented as memory within the CEOengine. The LTM can be designed as a removable module, so that it can besaved for archiving purposes as needed.

One of the tasks handled by the CEO engine is assembling the STM blocksand coordinating the transfer of information to the LTM blocks. Inaddition, once the tags are generated and STM blocks are assembled, theCEO engine has access to a lot of well-organized information which formsthe basis of efficient operations for robust organization and planning.These operations are controlled by the CEO engine.

FIG. 15 shows TIBIS operations that are facilitated by the CEO engine.As shown, the main functions/sub-modules of the CEO engine (which isrepresented by the dashed box) are:

Event Reporter. Collects information from stored tags and generatesstatistics on specific categories.

Event Manager: Monitors all current and short term plans and updates thetiming schedule.

Event Scheduler Monitors all module and machine generated requests forautomated actions and places entries in the schedule.

Task Manager: Collects all requests for automated user and machinegenerated tasks and contacts the communications module for data, voicecommunication when available to perform automated tasks.

Module Data Manager and Module Tag Manager: Generate control signal torelease data to/from the data exchange block and send and receive taginformation from specific modules to the CEO engine to perform TIBISrelated tasks.

User Interface (UI) Manager: Interfaces all time/event managementfunctions to the user interface blocks driving this information to theuser interface based on user request profiles. The UI Manager blocktakes the prioritized tasks and events as well as “stats” and “plans”supplied by the elements in the GSM engine and displays the informationaccording to a pre-selected format onto the display.

(2C) Store-Well, Retrieve-Well™

The current state of the Internet is an excellent example of whathappens when all sorts of information is available to users in anunorganized manner the problem is how does one find what one is lookingfor. Design of the next level of search algorithms, semantics web, videosearch, etc. is well under way, and undoubtedly there will beimprovements. It remains, however, that information is being added tothe Web at a far greater rate than the rate at which the algorithms areimproving.

The problem of information retrieval for a mobile user can be addressedby an integrated solution that will now be described. For organizationand storage, the solution introduced here provides a mechanism tocollect enough information from the user to be able to automaticallystore the information in an appropriate manner and retrieve it easilywithout resorting to a complex and computationally intensive search.Even though it is comfortable to talk about “locations” when discussingfiles and information (something inherited from folders in file drawersdays), it is becoming irrelevant and quite limiting to discuss locationswhen there are millions of files and bits of information generated everyhour. It is more appropriate to understand the uniqueness of eachmultimedia file as it is received/acquired and store it in a way thatfuture retrieval is seamless to the user and archiving, backup,deletions, etc. happen automatically. Such an approach increasesproductivity while reducing security and accessibility issues.

As described above, based on information type, user selection, activityand usage model the system generates and updates multi-dimensional tagsfor each piece of information (e.g. audio file, email, etc.) that thesystem handles. For each search/inquiry, a corresponding search tag isgenerated. The search tag is compared with the stored information tagsby in at least some instances by pure hardware (i.e., without usingsoftware), resulting in a very fast search. Content addressable memory(CAM) technology can be used to provide high-speed implementation. Acombination of hardware and software implementation can be used for thetag and content searches in certain instances, depending on the specificnature of the search. FIG. 16 illustrates the intelligent storage,search and retrieval technique described here, according to oneembodiment.

(3) System-Level View

FIG. 17 shows an overall system level view of functions of a mobiledevice such as described above, according to one embodiment. Alloperations within the mobile device can have a combination of softwareand hardware elements, with the CEO engine operations being primarilyhardware-based. The CEO engine manages functional module operations anddoes STM and LTM management. The TIBIS engine encompasses the GSMoperations within the CEO engine and manages the relevant operations forevent handling.

The techniques introduced above can be implemented in software and/orfirmware in conjunction with programmable circuitry, or entirely inspecial-purpose hardwired circuitry, or in a combination of suchembodiments. Special-purpose hardwired circuitry may be in the form of,for example, one or more application-specific integrated circuits(ASICs), programmable logic devices (PLDs), field-programmable gatearrays (FPGAs), etc.

Software or firmware to implement the techniques introduced here may bestored on a machine-readable medium and may be executed by one or moregeneral-purpose or special-purpose programmable microprocessors. A“machine-readable storage medium”, as the term is used herein, includesany mechanism that can store information in a form accessible by amachine (a machine may be, for example, a computer, network device,cellular phone, personal digital assistant (PDA), manufacturing tool,any device with one or more processors, etc.). For example, amachine-accessible medium includes recordable/non-recordable media(e.g., read-only memory (ROM); random access memory (RAM); magnetic diskstorage media; optical storage media; flash memory devices; etc.), etc.

The term “logic”, as used herein, can include, for example,special-purpose hardwired circuitry, software and/or firmware inconjunction with programmable circuitry, or a combination thereof.

Although the present invention has been described with reference tospecific exemplary embodiments, it will be recognized that the inventionis not limited to the embodiments described, but can be practiced withmodification and alteration within the spirit and scope of the appendedclaims. Accordingly, the specification and drawings are to be regardedin an illustrative sense rather than a restrictive sense.

What is claimed is:
 1. A wearable electronic device comprising: a coreengine including a processing element and a memory element operablyconnected to said processing element, two or more components eachincluding a processing element and a memory element operably connectedto said processing element, a data exchange block, one or more wearablemechanisms, wherein each of said components is independently functionaland dedicated to perform a designated functionality, wherein said deviceis configured to be worn on the body of the user of said device througha wearable mechanism, wherein said components and said core engineelectrically connect through said wearable mechanism, wherein one ormore of said components is detachable from said wearable mechanism andis independently operable, wherein said core engine coordinates theoperation of said device through communicating with said componentssolely through control bits, wherein said core engine through saidcontrol bits enables direct component to component transfer of dataamong two or more of said components with different data interfacecharacteristics by facilitating assembling or disassembling of data atthe component interface of one of said components to match the othercomponent's data bit width and timing, and wherein data transfer occursamong said two or more components in attached mode through said dataexchange block without transfer of data to or from said core engine. 2.The device of claim 1, wherein said components are swappable with othercomponents to change functionality or form factor of said device.
 3. Thedevice of claim 1, wherein at least one of said components provideswireless connectivity to a cellular or wide-area network, and isremovable, enabling an upgrade to wireless communication technology or achange in wireless service provider without modification to the mobiledevice or any other components of the device.
 4. The device of claim 1,wherein one of said components provides data and voice communicationcapability including microphone and speaker, and is detachable from saidwearable mechanism and is independently operable.
 5. The device of claim1, wherein at least one component has a battery and can charge thewearable device or another component.
 6. The device of claim 1, whereinthe memory element of one or more of said components includes data andtags, wherein said tags are content metadata for data elements withinsaid components, wherein said core engine receives said tag informationfrom said components.
 7. The device of claim 1, wherein said core enginekeeps track of the components with displays that are presently attachedto said wearable mechanism and wherein said core engine sends theappropriate control signals to the circuitry for resizing the imageappropriately to resize the screen so said device has a larger displayin attached mode comprised of said smaller displays.
 8. An electronicdevice comprising: a core engine including a processing element and amemory element operably connected to said processing element, two ormore components each including a processing element and a memory elementoperably connected to said processing element, one or more detacheddisplays, a data exchange block, wherein each of said components areindependently functional and dedicated to perform a designatedfunctionality, wherein said device is further comprised of a housingunit, wherein said components and said core engine electrically connectthrough said housing unit, wherein said core engine coordinates theoperation of said device through communicating with said components andsaid one or more displays solely through control bits, wherein said coreengine through said control bits enables direct component to componenttransfer of data among two or more of said components with differentdata interface characteristics by facilitating assembling ordisassembling of data at the component interface of one of saidcomponents to match the other component's data bit width and timing,wherein one or more of said components are detachable from said housingunit, wherein data is transferred among two or more of said componentsin attached mode, through said data exchange block, without data beingtransferred to or from said core engine.
 9. The device of claim 8,wherein said components are swappable with other components to changefunctionality or form factor of said device.
 10. The device of claim 8,wherein at least one of said components provides wireless connectivityto a cellular or wide-area network, and is removable, enabling anupgrade to wireless communication technology or a change in wirelessservice provider without modification to the mobile device or any othercomponents of the device.
 11. The device of claim 8, wherein one of saidcomponents provides data and voice communication capability includingmicrophone and speaker, and is detachable from the housing and isindependently operable.
 12. The device of claim 8, wherein the memoryelement of one or more of said components includes data and tags,wherein said tags are content metadata for data elements within saidcomponents, wherein said core engine receives said tag information fromsaid components.
 13. The device of claim 8, wherein said core enginekeeps track of the components with displays and individual display unitsthat are presently attached to said housing and sends the appropriatecontrol signals to the circuitry for resizing the image appropriately toresize the screen so said device has a larger display in attached modecomprised of said smaller displays.
 14. A method for an electronicdevice comprising: said device comprising of two or more functionallyindependent components, one or more wearable mechanisms, a data exchangeblock, a core engine, wherein, said wearable mechanism electricallyconnecting said components and said core engine, wherein one or more ofsaid components detaching from said wearable mechanism are independentlyoperable and designated to perform a specific functionality, whereinsaid two or more components comprising of a processing element and amemory element operably connected to said processing element, whereinsaid core engine coordinating the operation of said device, wherein saidcore engine communicating with said components solely through controlbits, wherein said core engine's control bits enabling direct componentto component transfer of data among two or more of said components withdifferent data interface characteristics by facilitating assembling ordisassembling of data at the component interface of one of saidcomponents to match the other component's data bit width and timing,wherein two or more of said components in attached mode, transferringdata directly to each other through said data exchange block withoutdata being transferred to or from said core engine.
 15. The method ofclaim 14, wherein said housing unit includes a wearable mechanismcapable of attaching to the body of a user.
 16. A method for anelectronic device comprising: said device comprising of two or morefunctionally independent components, a housing unit, a data exchangeblock, a core engine, one or more detached displays, wherein, saidhousing unit electrically connecting said components and said coreengine, wherein one or more of said components detaching from saidhousing unit is independently operable and designated to performing aspecific functionality, wherein two or more of said componentscomprising of a processing element and a memory element, said coreengine coordinating the operation of said device, said core enginecommunicating with said components solely through control bits, whereinsaid core engine enabling direct component to component transfer of dataamong two or more of said components with different data interfacecharacteristics by facilitating assembling or disassembling of data atthe component interface of one of said components to match the othercomponent's data bit width and timing, wherein two or more of saidcomponents in attached mode, transferring data directly to each otherthrough said data exchange block without data being transferred to orfrom said core engine.